Implemented option for comma separated slice data #3
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
written tests for decoding comma separated arrays
|
Yeah I forgot to check the repo activity! In that case, feel free to PR your addition to my fork, might as well keep a single copy for future users. |
update readme with a maintenance notice and new import paths add go.mod file
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves #2
commaoption set results in a single parameter with comma separated values. It's the most basic implementation and will not attempt to escape commas that exist within strings.commaoption set will treat input as a singleurl.Valuesitem and runstrings.Spliton it to produce an iterable for conversion. Will not attempt to handle escaped commas within strings. Only tested with primitive types.omitemptynote.